Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11f3d14a519bb657c224bf1944fcde0e30cceebd5b6e098a25e4401b300f4903

Tx prefix hash: 11be017c7a580429e73fae8ed99625c637e73e3d9c8fb13721b80d24bd762cd2
Tx public key: b31712f66284b43a5e1c7de7718f0d6094fd587b3bdbae4768672ba06ecd3efc
Timestamp: 1743178320 Timestamp [UCT]: 2025-03-28 16:12:00 Age [y:d:h:m:s]: 00:238:07:00:15
Block: 1249221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168047 RingCT/type: yes/0
Extra: 01b31712f66284b43a5e1c7de7718f0d6094fd587b3bdbae4768672ba06ecd3efc0211000000019ba629df000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 691704dc0fe9d38d4bb85c8bd3b8c8b3a2141ea82631e56856d3222d2022c9e8 0.600000000000 1736258 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": 1249231, "vin": [ { "gen": { "height": 1249221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "691704dc0fe9d38d4bb85c8bd3b8c8b3a2141ea82631e56856d3222d2022c9e8" } } ], "extra": [ 1, 179, 23, 18, 246, 98, 132, 180, 58, 94, 28, 125, 231, 113, 143, 13, 96, 148, 253, 88, 123, 59, 219, 174, 71, 104, 103, 43, 160, 110, 205, 62, 252, 2, 17, 0, 0, 0, 1, 155, 166, 41, 223, 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