Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5854035e080e8e2c25483717b14cb741c8922e938da6ebef4bedec91db8ecde

Tx prefix hash: 6980467381a73bbc146858ef2b61cb86ba386c65af8c3a2aa29f3119c5a828f7
Tx public key: 348062ba1ca68bf3d0c3f52a839ffcb8641fb32be919f3f9d467a01225b18b05
Timestamp: 1745070522 Timestamp [UCT]: 2025-04-19 13:48:42 Age [y:d:h:m:s]: 00:216:12:14:45
Block: 1264894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152456 RingCT/type: yes/0
Extra: 01348062ba1ca68bf3d0c3f52a839ffcb8641fb32be919f3f9d467a01225b18b050211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 662d52fd7591332cc7805589e7a8806c06f258d60d8ca2e41b7852bd6f997b7e 0.600000000000 1752095 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": 1264904, "vin": [ { "gen": { "height": 1264894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "662d52fd7591332cc7805589e7a8806c06f258d60d8ca2e41b7852bd6f997b7e" } } ], "extra": [ 1, 52, 128, 98, 186, 28, 166, 139, 243, 208, 195, 245, 42, 131, 159, 252, 184, 100, 31, 179, 43, 233, 25, 243, 249, 212, 103, 160, 18, 37, 177, 139, 5, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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