Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afe7f2e761d78299c6e215f961cb1c8a2f59042864fdd0c8b36bdb427f3ed459

Tx prefix hash: d243116de753673a02c8665722ab318c648cd23527a56837adae1f465366d1ac
Tx public key: 3897672880f92b022fe9e7d1faf73a1f8a16b8c88044b4c57a879599ef0bfd33
Timestamp: 1737566902 Timestamp [UCT]: 2025-01-22 17:28:22 Age [y:d:h:m:s]: 00:146:07:35:17
Block: 1202996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104314 RingCT/type: yes/0
Extra: 013897672880f92b022fe9e7d1faf73a1f8a16b8c88044b4c57a879599ef0bfd33021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac44c7b57776426213a4b3357d4f1d0ea525398bdef65fce0d11b7697006dd4e 0.600000000000 1689667 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": 1203006, "vin": [ { "gen": { "height": 1202996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac44c7b57776426213a4b3357d4f1d0ea525398bdef65fce0d11b7697006dd4e" } } ], "extra": [ 1, 56, 151, 103, 40, 128, 249, 43, 2, 47, 233, 231, 209, 250, 247, 58, 31, 138, 22, 184, 200, 128, 68, 180, 197, 122, 135, 149, 153, 239, 11, 253, 51, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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