Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 786cbc5accb07d6e749ca494b4e7aae2733ebfabaf2e0110e935e2ca376f349b

Tx prefix hash: afe2c66204f11b9bfca33ecb9ad70de7c2a3eb4fac1658fe2b173828cf1eafd8
Tx public key: b8f37ec411986fb9c69de39cb9e413200801a417439f749d3836b1a48f7c614b
Timestamp: 1744226145 Timestamp [UCT]: 2025-04-09 19:15:45 Age [y:d:h:m:s]: 00:287:02:45:59
Block: 1257892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202879 RingCT/type: yes/0
Extra: 01b8f37ec411986fb9c69de39cb9e413200801a417439f749d3836b1a48f7c614b0211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b287cec5a7ac36aacb8223d2bf38014fe4864b96281fe13bcebe6e41866a1e79 0.600000000000 1745023 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": 1257902, "vin": [ { "gen": { "height": 1257892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b287cec5a7ac36aacb8223d2bf38014fe4864b96281fe13bcebe6e41866a1e79" } } ], "extra": [ 1, 184, 243, 126, 196, 17, 152, 111, 185, 198, 157, 227, 156, 185, 228, 19, 32, 8, 1, 164, 23, 67, 159, 116, 157, 56, 54, 177, 164, 143, 124, 97, 75, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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