Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d04318d7ec6077f44ecca7358ac8b2feab455d75cb808e81c86d17f5f9c30c

Tx prefix hash: 4b216c2cbf94895b73a87ed5e21ad3e7fe12ba9175313316fbeef6a296fc4360
Tx public key: 0fec2adb36ea477d7629402a5503e9fad0caa638b0cbfb280e9c1da12f3d006f
Timestamp: 1763577405 Timestamp [UCT]: 2025-11-19 18:36:45 Age [y:d:h:m:s]: 00:034:05:40:36
Block: 1415705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24510 RingCT/type: yes/0
Extra: 010fec2adb36ea477d7629402a5503e9fad0caa638b0cbfb280e9c1da12f3d006f02110000000217b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cd9491172c4ea9b03a2d0d06d5f0cbe611bb6fb147fe00c1bd0410bf5c2978f 0.600000000000 1904210 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": 1415715, "vin": [ { "gen": { "height": 1415705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cd9491172c4ea9b03a2d0d06d5f0cbe611bb6fb147fe00c1bd0410bf5c2978f" } } ], "extra": [ 1, 15, 236, 42, 219, 54, 234, 71, 125, 118, 41, 64, 42, 85, 3, 233, 250, 208, 202, 166, 56, 176, 203, 251, 40, 14, 156, 29, 161, 47, 61, 0, 111, 2, 17, 0, 0, 0, 2, 23, 177, 145, 50, 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