Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 368e0618dba92af0501869454114a8693f4ccd7d831b5a72c56de9fae196d293

Tx prefix hash: 42b1d5c06a8a9c9b3f961887a187a9b04be707ff7bb841d0e88ebb997eb234eb
Tx public key: 9894bd0ba05cbcb2d1e54299508b2f7f3f513e6e0db329ef6f3f4824d428d1d0
Timestamp: 1766271234 Timestamp [UCT]: 2025-12-20 22:53:54 Age [y:d:h:m:s]: 00:000:21:56:53
Block: 1438033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 643 RingCT/type: yes/0
Extra: 019894bd0ba05cbcb2d1e54299508b2f7f3f513e6e0db329ef6f3f4824d428d1d00211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87ad03f9e66c7ee13261214c21b00acda26eaf185ddfe5fc658a4bd05cd130ea 0.600000000000 1926848 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": 1438043, "vin": [ { "gen": { "height": 1438033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87ad03f9e66c7ee13261214c21b00acda26eaf185ddfe5fc658a4bd05cd130ea" } } ], "extra": [ 1, 152, 148, 189, 11, 160, 92, 188, 178, 209, 229, 66, 153, 80, 139, 47, 127, 63, 81, 62, 110, 13, 179, 41, 239, 111, 63, 72, 36, 212, 40, 209, 208, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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