Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f877bb66a25c05426a0207fe422fdd00810f0d5dbaab9a66d1f0891e32fa3843

Tx prefix hash: c0ac9c178057b8fa15b8da853c0da212b8bb81461fba6ee6f1a094cdbc6a2114
Tx public key: 187d28e9d1f57f2a60f7fb1cfda55bf778260267a269384f5d6e9322f008ef5e
Timestamp: 1725726989 Timestamp [UCT]: 2024-09-07 16:36:29 Age [y:d:h:m:s]: 00:272:17:53:24
Block: 1105040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194817 RingCT/type: yes/0
Extra: 01187d28e9d1f57f2a60f7fb1cfda55bf778260267a269384f5d6e9322f008ef5e021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f6bf1829797d71ba52704e787da5d08c1fbbba87a573543b9978f82684c4014 0.600000000000 1582377 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": 1105050, "vin": [ { "gen": { "height": 1105040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f6bf1829797d71ba52704e787da5d08c1fbbba87a573543b9978f82684c4014" } } ], "extra": [ 1, 24, 125, 40, 233, 209, 245, 127, 42, 96, 247, 251, 28, 253, 165, 91, 247, 120, 38, 2, 103, 162, 105, 56, 79, 93, 110, 147, 34, 240, 8, 239, 94, 2, 17, 0, 0, 0, 7, 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