Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b31e68f379b372b8f1f32b67a04bfedb236c6437d2a0cc8d7f9c2739b2cdedaa

Tx prefix hash: 4299d1967941449c2dc169a39fe9a3441113961588fa962d8b9b10a7c77b80a5
Tx public key: 500beea111e165afb69c050593773ad10d7c83e38ae74afd1df115dcfd47a4ee
Timestamp: 1749668456 Timestamp [UCT]: 2025-06-11 19:00:56 Age [y:d:h:m:s]: 00:195:08:50:56
Block: 1302947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137368 RingCT/type: yes/0
Extra: 01500beea111e165afb69c050593773ad10d7c83e38ae74afd1df115dcfd47a4ee0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d7fc4f5cec6c2378fe6929e6054c8b0e5a3bbc6ab53b0138053d24dd49ecc5e 0.600000000000 1790522 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": 1302957, "vin": [ { "gen": { "height": 1302947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d7fc4f5cec6c2378fe6929e6054c8b0e5a3bbc6ab53b0138053d24dd49ecc5e" } } ], "extra": [ 1, 80, 11, 238, 161, 17, 225, 101, 175, 182, 156, 5, 5, 147, 119, 58, 209, 13, 124, 131, 227, 138, 231, 74, 253, 29, 241, 21, 220, 253, 71, 164, 238, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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