Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e52319eab679f2cc8e76d9d78fc01b82b06b5a0ef49b65c215889aa593914f2

Tx prefix hash: e518912b4d1473f42cfaf4db9cacbc36bad060a71585eb0f703a53db8ef99ab7
Tx public key: 0c8301fcd7c90daa694b0e70e43bac108e3a4e7c900e156ef82325379ed15f9f
Timestamp: 1720334834 Timestamp [UCT]: 2024-07-07 06:47:14 Age [y:d:h:m:s]: 00:231:03:56:08
Block: 1060330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165116 RingCT/type: yes/0
Extra: 010c8301fcd7c90daa694b0e70e43bac108e3a4e7c900e156ef82325379ed15f9f02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24e60fbb94fb89db62690c090d72258a6921fbbaf1a017c5f1a698b55618be5d 0.600000000000 1530807 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": 1060340, "vin": [ { "gen": { "height": 1060330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24e60fbb94fb89db62690c090d72258a6921fbbaf1a017c5f1a698b55618be5d" } } ], "extra": [ 1, 12, 131, 1, 252, 215, 201, 13, 170, 105, 75, 14, 112, 228, 59, 172, 16, 142, 58, 78, 124, 144, 14, 21, 110, 248, 35, 37, 55, 158, 209, 95, 159, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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