Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8785bd3b2e495af9cb1b59bb46bbddbaa1909d6ea5f0785273402e718f56629

Tx prefix hash: 7d62ef29e3034e8b1d9dc80afa6e7331ab1ef557ae34c3770037c496f710fdb6
Tx public key: ce341187fe5aff4ead7c95e883311e8aeca7fd64c388be0621f8a364f047a1e1
Timestamp: 1756320232 Timestamp [UCT]: 2025-08-27 18:43:52 Age [y:d:h:m:s]: 00:152:02:08:47
Block: 1355750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108527 RingCT/type: yes/0
Extra: 01ce341187fe5aff4ead7c95e883311e8aeca7fd64c388be0621f8a364f047a1e10211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f25bda89b15835cea6ba5a053afd88d35a5200db0bed66bd8c95430d37e657a 0.600000000000 1843753 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": 1355760, "vin": [ { "gen": { "height": 1355750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f25bda89b15835cea6ba5a053afd88d35a5200db0bed66bd8c95430d37e657a" } } ], "extra": [ 1, 206, 52, 17, 135, 254, 90, 255, 78, 173, 124, 149, 232, 131, 49, 30, 138, 236, 167, 253, 100, 195, 136, 190, 6, 33, 248, 163, 100, 240, 71, 161, 225, 2, 17, 0, 0, 0, 1, 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