Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff1a70afc4ccec39ea197d7a8dd615d45f6ec74dc3f395a79475f8987c3247b8

Tx prefix hash: 1ab365d8de63ce47b93d6b0b6f5d67cacba9a0e44b197d3fbe4abb1ea1ee772e
Tx public key: 3d5944835ad576d5539392e9662f17cfdbdc3c7bc1f0f3afd0aea485c7791411
Timestamp: 1758396300 Timestamp [UCT]: 2025-09-20 19:25:00 Age [y:d:h:m:s]: 00:076:03:03:17
Block: 1372767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54505 RingCT/type: yes/0
Extra: 013d5944835ad576d5539392e9662f17cfdbdc3c7bc1f0f3afd0aea485c7791411021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a272f4081323dc5e11e30aaaf8c5d05e6d274958e83a92a45b3d6ccf5ad15b2 0.600000000000 1860852 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": 1372777, "vin": [ { "gen": { "height": 1372767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a272f4081323dc5e11e30aaaf8c5d05e6d274958e83a92a45b3d6ccf5ad15b2" } } ], "extra": [ 1, 61, 89, 68, 131, 90, 213, 118, 213, 83, 147, 146, 233, 102, 47, 23, 207, 219, 220, 60, 123, 193, 240, 243, 175, 208, 174, 164, 133, 199, 121, 20, 17, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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