Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa83ef99462c07c55a5801702b766664d56a1bee7a907bfd73e48ac52a372827

Tx prefix hash: 28841d3780a6b9646204364a37caea9c604bad3a8eefdbe9f47e29165a6e7e7a
Tx public key: bedc61823e6e038b1e74a9123a7d065aff3d5be99a574ad4e5ae107720c72000
Timestamp: 1717729775 Timestamp [UCT]: 2024-06-07 03:09:35 Age [y:d:h:m:s]: 00:178:14:25:57
Block: 1038735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127834 RingCT/type: yes/0
Extra: 01bedc61823e6e038b1e74a9123a7d065aff3d5be99a574ad4e5ae107720c7200002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93c5cb7b7cf1e5fd9450c64c37cede78762e55f40b74f4408a2332966e9e3535 0.600000000000 1507296 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": 1038745, "vin": [ { "gen": { "height": 1038735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93c5cb7b7cf1e5fd9450c64c37cede78762e55f40b74f4408a2332966e9e3535" } } ], "extra": [ 1, 190, 220, 97, 130, 62, 110, 3, 139, 30, 116, 169, 18, 58, 125, 6, 90, 255, 61, 91, 233, 154, 87, 74, 212, 229, 174, 16, 119, 32, 199, 32, 0, 2, 17, 0, 0, 0, 1, 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