Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f666ec84b68d2085c873fdd934a3e8a957ce978e9714df979ae714c9e1f8abac

Tx prefix hash: 662e40f602c20ea93f0964392397e00db3ebc78bbb932dd8f0152702eb306bdc
Tx public key: 552850d929c144121fa62af07119fbef6c44fc9afb16c63fda6ba8f2c1de9f8b
Timestamp: 1726639049 Timestamp [UCT]: 2024-09-18 05:57:29 Age [y:d:h:m:s]: 00:238:03:44:18
Block: 1112591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170071 RingCT/type: yes/0
Extra: 01552850d929c144121fa62af07119fbef6c44fc9afb16c63fda6ba8f2c1de9f8b02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00be8bbbf43c824f3e3f90f0f981790af41afaa0a5f6e153b7261a919317ef37 0.600000000000 1591966 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1112601, "vin": [ { "gen": { "height": 1112591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00be8bbbf43c824f3e3f90f0f981790af41afaa0a5f6e153b7261a919317ef37" } } ], "extra": [ 1, 85, 40, 80, 217, 41, 193, 68, 18, 31, 166, 42, 240, 113, 25, 251, 239, 108, 68, 252, 154, 251, 22, 198, 63, 218, 107, 168, 242, 193, 222, 159, 139, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8