Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 357db8e7af756d5a4f45b22d4c60bb8cc6ca5e9656a919ac4fef60427e773edc

Tx prefix hash: 9347e5db270a56ead5a5702a9f1c83ac2623f4bffd9e5f6cf25050b613f0f7da
Tx public key: 5121af89fc6ec3b644f224ddecf2601d64ce5e70c32281de91c8c2220462470f
Timestamp: 1716649779 Timestamp [UCT]: 2024-05-25 15:09:39 Age [y:d:h:m:s]: 00:294:08:14:08
Block: 1029786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210390 RingCT/type: yes/0
Extra: 015121af89fc6ec3b644f224ddecf2601d64ce5e70c32281de91c8c2220462470f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c324b45dc80383ec02850f0f29b0885a399a7c82a3a87f74862708a7a865c1b1 0.600000000000 1497971 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": 1029796, "vin": [ { "gen": { "height": 1029786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c324b45dc80383ec02850f0f29b0885a399a7c82a3a87f74862708a7a865c1b1" } } ], "extra": [ 1, 81, 33, 175, 137, 252, 110, 195, 182, 68, 242, 36, 221, 236, 242, 96, 29, 100, 206, 94, 112, 195, 34, 129, 222, 145, 200, 194, 34, 4, 98, 71, 15, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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