Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdbc5e0faee124f72c708dc5b83018af23bc17de7d0ac593f1d478e911762667

Tx prefix hash: fd5c9390756366422c8f39d0e6e5755b6c4ba131ad78f482c936dafc3afc5bd1
Tx public key: 9ee00b3fe8fbb05cf3a67895bc19e9d7c6fb4554bb1b650fd6f6fbeb429b9559
Timestamp: 1761771193 Timestamp [UCT]: 2025-10-29 20:53:13 Age [y:d:h:m:s]: 00:054:23:51:59
Block: 1400753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39355 RingCT/type: yes/0
Extra: 019ee00b3fe8fbb05cf3a67895bc19e9d7c6fb4554bb1b650fd6f6fbeb429b955902110000000a25a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b71e61654b3ee79bedcd0b574da85af2090b71257de5e86757c498a0377ec00a 0.600000000000 1889070 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": 1400763, "vin": [ { "gen": { "height": 1400753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b71e61654b3ee79bedcd0b574da85af2090b71257de5e86757c498a0377ec00a" } } ], "extra": [ 1, 158, 224, 11, 63, 232, 251, 176, 92, 243, 166, 120, 149, 188, 25, 233, 215, 198, 251, 69, 84, 187, 27, 101, 15, 214, 246, 251, 235, 66, 155, 149, 89, 2, 17, 0, 0, 0, 10, 37, 163, 90, 15, 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