Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c12044e768d54a5ddbc8e753cb4bad9c344b0f2669a211121de412d0a16a89b

Tx prefix hash: fca08af5bb9519c1bd0e0eb380e1837ef18af8d80e0864021db719acc8a88981
Tx public key: 35c814ab038a486cfbb88ad490e5a9c1c68b5c6cd22ab65c7547c90daa88e286
Timestamp: 1721159058 Timestamp [UCT]: 2024-07-16 19:44:18 Age [y:d:h:m:s]: 00:221:07:53:02
Block: 1067176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158057 RingCT/type: yes/0
Extra: 0135c814ab038a486cfbb88ad490e5a9c1c68b5c6cd22ab65c7547c90daa88e286021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 631d5bc9653ed787093a2d35d5f3325eee56ea10fc489268fc4ccd1e8fd507bf 0.600000000000 1537919 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": 1067186, "vin": [ { "gen": { "height": 1067176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "631d5bc9653ed787093a2d35d5f3325eee56ea10fc489268fc4ccd1e8fd507bf" } } ], "extra": [ 1, 53, 200, 20, 171, 3, 138, 72, 108, 251, 184, 138, 212, 144, 229, 169, 193, 198, 139, 92, 108, 210, 42, 182, 92, 117, 71, 201, 13, 170, 136, 226, 134, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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