Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0ec1d3c5a22cfdbed95318ea2ff38a6438feaeec7cabb14626fcf51d56f655d

Tx prefix hash: c685fe47e066263e7cb156c9b38ac44fe98ceefcf05e2cbe4e15ce9a2da17183
Tx public key: f4887c90dc0ad52a5e3583ca5dccf98c407d57ae68f4bc51b0d745afd7bdb757
Timestamp: 1728409542 Timestamp [UCT]: 2024-10-08 17:45:42 Age [y:d:h:m:s]: 00:217:10:53:56
Block: 1127275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155233 RingCT/type: yes/0
Extra: 01f4887c90dc0ad52a5e3583ca5dccf98c407d57ae68f4bc51b0d745afd7bdb757021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d9c3cec642a04ed0dd278270ed93705c9e8d4881955fdc567117a4ce8769b1d 0.600000000000 1610076 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": 1127285, "vin": [ { "gen": { "height": 1127275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d9c3cec642a04ed0dd278270ed93705c9e8d4881955fdc567117a4ce8769b1d" } } ], "extra": [ 1, 244, 136, 124, 144, 220, 10, 213, 42, 94, 53, 131, 202, 93, 204, 249, 140, 64, 125, 87, 174, 104, 244, 188, 81, 176, 215, 69, 175, 215, 189, 183, 87, 2, 17, 0, 0, 0, 5, 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