Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a02a2397ab994787edd361ae05a2504509a92535f8a047ed53221580901ce3b

Tx prefix hash: 2f29e87aa3108560b7a537eae19082816936368efe73a03220778945637292fe
Tx public key: 331bdbf0abf15c31269c50abe1098a9ae887d1b568b0f2e410e9240e7c37accc
Timestamp: 1701641452 Timestamp [UCT]: 2023-12-03 22:10:52 Age [y:d:h:m:s]: 01:170:21:04:59
Block: 905350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383327 RingCT/type: yes/0
Extra: 01331bdbf0abf15c31269c50abe1098a9ae887d1b568b0f2e410e9240e7c37accc02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.614044148000 dcy

stealth address amount amount idx
00: 0fbd27285782cb10d42a95c9519e7015d11c0c934d5a9114a7d15434526d8a1e 0.614044148000 1362233 of 0

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": 905360, "vin": [ { "gen": { "height": 905350 } } ], "vout": [ { "amount": 614044148, "target": { "key": "0fbd27285782cb10d42a95c9519e7015d11c0c934d5a9114a7d15434526d8a1e" } } ], "extra": [ 1, 51, 27, 219, 240, 171, 241, 92, 49, 38, 156, 80, 171, 225, 9, 138, 154, 232, 135, 209, 181, 104, 176, 242, 228, 16, 233, 36, 14, 124, 55, 172, 204, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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