Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b19537149fd076b8796c765b64d64b8dee3c80bf475bc047459fbcfdfc83fde8

Tx prefix hash: 4267f947c3be7d0d2d9724c979869f463c4b1471904135e4a53a80eec931f808
Tx public key: 34a6f2122499927d23873d112e9c2dcb4783852e88821aed79911c876d2519d2
Timestamp: 1726264669 Timestamp [UCT]: 2024-09-13 21:57:49 Age [y:d:h:m:s]: 00:207:13:58:35
Block: 1109487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148201 RingCT/type: yes/0
Extra: 0134a6f2122499927d23873d112e9c2dcb4783852e88821aed79911c876d2519d2021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a9187840dce7d97ef73fce1c8b2fdc35bc3e7b759d06827d186b88c30c1aec3 0.600000000000 1587758 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": 1109497, "vin": [ { "gen": { "height": 1109487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a9187840dce7d97ef73fce1c8b2fdc35bc3e7b759d06827d186b88c30c1aec3" } } ], "extra": [ 1, 52, 166, 242, 18, 36, 153, 146, 125, 35, 135, 61, 17, 46, 156, 45, 203, 71, 131, 133, 46, 136, 130, 26, 237, 121, 145, 28, 135, 109, 37, 25, 210, 2, 17, 0, 0, 0, 3, 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