Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac0afe1e2d6856eefbf3ad6dc19c47d4e0f7aeb755f46ddc3aa8d66ff584b334

Tx prefix hash: 8149b32d3f68859aafa6e733707316746191a66d745d26c2799ebfe637b43ed5
Tx public key: 5d4de3d46056d240e53c2e6b59d3443e364e3985cc032e781c2421e58008ba0a
Timestamp: 1712169834 Timestamp [UCT]: 2024-04-03 18:43:54 Age [y:d:h:m:s]: 00:295:18:23:46
Block: 992610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211695 RingCT/type: yes/0
Extra: 015d4de3d46056d240e53c2e6b59d3443e364e3985cc032e781c2421e58008ba0a02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cab26f6d3210d7151714a9201d6c2184ca3b0bdda3856527bc3253c313671a3 0.600000000000 1452974 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": 992620, "vin": [ { "gen": { "height": 992610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cab26f6d3210d7151714a9201d6c2184ca3b0bdda3856527bc3253c313671a3" } } ], "extra": [ 1, 93, 77, 227, 212, 96, 86, 210, 64, 229, 60, 46, 107, 89, 211, 68, 62, 54, 78, 57, 133, 204, 3, 46, 120, 28, 36, 33, 229, 128, 8, 186, 10, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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