Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e322746ba95d55aab54613007cbc541c5549825884dcaaec584864c0d5b8e6b

Tx prefix hash: b1834eb6595289317dc3edf86a469188b35f31c03dbd457ef10b113d7f27158a
Tx public key: c66b9afa59ac550ccfad18b34c5efe4c2d211ab6b15b7ea864a0821d759a328e
Timestamp: 1704550314 Timestamp [UCT]: 2024-01-06 14:11:54 Age [y:d:h:m:s]: 01:117:18:32:11
Block: 929449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345313 RingCT/type: yes/0
Extra: 01c66b9afa59ac550ccfad18b34c5efe4c2d211ab6b15b7ea864a0821d759a328e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0db7ece71fa410b28c8a3e17bb0d0d3138974fef0c18710ccb10ed3f1f92addb 0.600000000000 1387321 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": 929459, "vin": [ { "gen": { "height": 929449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0db7ece71fa410b28c8a3e17bb0d0d3138974fef0c18710ccb10ed3f1f92addb" } } ], "extra": [ 1, 198, 107, 154, 250, 89, 172, 85, 12, 207, 173, 24, 179, 76, 94, 254, 76, 45, 33, 26, 182, 177, 91, 126, 168, 100, 160, 130, 29, 117, 154, 50, 142, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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