Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d789b4f84e2b9c8006c53fd6bb208c036b54bcf5cb9172c17c46da9be64048d

Tx prefix hash: 3e1bbc401c8ae42a83c6a3f658c80d18da364d58480cc33187a4cbc453f598eb
Tx public key: 60fe0958b8514fa8bb609a6d3e56c58a75ac8bf860bfe3abc643c1781bd01d4d
Timestamp: 1729274878 Timestamp [UCT]: 2024-10-18 18:07:58 Age [y:d:h:m:s]: 00:354:17:45:11
Block: 1134454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250968 RingCT/type: yes/0
Extra: 0160fe0958b8514fa8bb609a6d3e56c58a75ac8bf860bfe3abc643c1781bd01d4d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 100d7e1813f7920cb84b59bf9945974a58f97614594c24099972b6ddf4c82906 0.600000000000 1617761 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": 1134464, "vin": [ { "gen": { "height": 1134454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "100d7e1813f7920cb84b59bf9945974a58f97614594c24099972b6ddf4c82906" } } ], "extra": [ 1, 96, 254, 9, 88, 184, 81, 79, 168, 187, 96, 154, 109, 62, 86, 197, 138, 117, 172, 139, 248, 96, 191, 227, 171, 198, 67, 193, 120, 27, 208, 29, 77, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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