Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcb54f3e2d9e2a780d578c7326c93e6b615b7dc5820762542ce670f705ef71d0

Tx prefix hash: ca6c5f45a355d58428012ad4917902e3189493b5eade366db965c01f211ce183
Tx public key: ed1f1fde332d4e47337eccf86798dcae66e75772a2de1ba25298d7a325b4ef5c
Timestamp: 1737277575 Timestamp [UCT]: 2025-01-19 09:06:15 Age [y:d:h:m:s]: 00:152:07:00:40
Block: 1200612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108548 RingCT/type: yes/0
Extra: 01ed1f1fde332d4e47337eccf86798dcae66e75772a2de1ba25298d7a325b4ef5c021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2e3d82edc7d06fabcee1e373bc67bc8cf8013f0023c6c5e6870dc970fb2be3b 0.600000000000 1687257 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": 1200622, "vin": [ { "gen": { "height": 1200612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2e3d82edc7d06fabcee1e373bc67bc8cf8013f0023c6c5e6870dc970fb2be3b" } } ], "extra": [ 1, 237, 31, 31, 222, 51, 45, 78, 71, 51, 126, 204, 248, 103, 152, 220, 174, 102, 231, 87, 114, 162, 222, 27, 162, 82, 152, 215, 163, 37, 180, 239, 92, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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