Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c18af00e42e4c5954af7946a4cbfb3bef59eb1384b8b41833c5ff1164c42531

Tx prefix hash: d7b015e777c60afca736c4a2efbc3fb796905f4fdcbdd466efbb3602aa641dab
Tx public key: d0791d407a0de5356d78abf1e9a7ad546b4e245dd371fbeceba9f63b018dcde9
Timestamp: 1706682824 Timestamp [UCT]: 2024-01-31 06:33:44 Age [y:d:h:m:s]: 01:076:11:01:49
Block: 947131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315726 RingCT/type: yes/0
Extra: 01d0791d407a0de5356d78abf1e9a7ad546b4e245dd371fbeceba9f63b018dcde90211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10e2933996fcd467680bd4f271a437e5296995ba7f73f0e460ae241dd015d594 0.600000000000 1405479 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": 947141, "vin": [ { "gen": { "height": 947131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10e2933996fcd467680bd4f271a437e5296995ba7f73f0e460ae241dd015d594" } } ], "extra": [ 1, 208, 121, 29, 64, 122, 13, 229, 53, 109, 120, 171, 241, 233, 167, 173, 84, 107, 78, 36, 93, 211, 113, 251, 236, 235, 169, 246, 59, 1, 141, 205, 233, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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