Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 670c9a3a8ec73000ab61ae42112e53a12cac3e7547b73855ecd74f20b3c94e13

Tx prefix hash: 21e5234b6fcc42a01a35d1c7662550b3c354ee6583f69c175d5f50cffedfe7b1
Tx public key: f1aa1570c472885ff8f4480fa01bef8b26f0bd0a3b033d05cd69bb5fb74b5204
Timestamp: 1702364834 Timestamp [UCT]: 2023-12-12 07:07:14 Age [y:d:h:m:s]: 01:039:13:43:16
Block: 911364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289588 RingCT/type: yes/0
Extra: 01f1aa1570c472885ff8f4480fa01bef8b26f0bd0a3b033d05cd69bb5fb74b5204021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea2da261515b0847c016f3942032ef8796495d0d165726dad93c44ac7b3c28f3 0.600000000000 1368549 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": 911374, "vin": [ { "gen": { "height": 911364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea2da261515b0847c016f3942032ef8796495d0d165726dad93c44ac7b3c28f3" } } ], "extra": [ 1, 241, 170, 21, 112, 196, 114, 136, 95, 248, 244, 72, 15, 160, 27, 239, 139, 38, 240, 189, 10, 59, 3, 61, 5, 205, 105, 187, 95, 183, 75, 82, 4, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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