Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a02f7d568e6ca3105b3ddf98a9c8c3e6959e673c85b66044b24cf1a8527839a

Tx prefix hash: 2fa62ec69e9cba35867d7b9413dfe9570cf6ed4cae6570ca6b09fc6e5ddcae87
Tx public key: 1de177d2e3194efd97f72b297ce02d8ce33cf027e56325fb33ff10a0d5bccafb
Timestamp: 1741246972 Timestamp [UCT]: 2025-03-06 07:42:52 Age [y:d:h:m:s]: 00:007:05:47:13
Block: 1233246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5192 RingCT/type: yes/0
Extra: 011de177d2e3194efd97f72b297ce02d8ce33cf027e56325fb33ff10a0d5bccafb021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e540c702ae33018bc6e5b53c23fbbbe4b5faea4791d66439603d09169d0f9af 0.600000000000 1720165 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": 1233256, "vin": [ { "gen": { "height": 1233246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e540c702ae33018bc6e5b53c23fbbbe4b5faea4791d66439603d09169d0f9af" } } ], "extra": [ 1, 29, 225, 119, 210, 227, 25, 78, 253, 151, 247, 43, 41, 124, 224, 45, 140, 227, 60, 240, 39, 229, 99, 37, 251, 51, 255, 16, 160, 213, 188, 202, 251, 2, 17, 0, 0, 0, 1, 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