Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6a77c67f45ab61c2d7a859dfaf8b6dde28db4b1337ffaae698cbfdc9e035a06

Tx prefix hash: 37acdaef2f9f50d26e75b42d0528102f58896d05e323dfbcc2909bf6551f554e
Tx public key: 05099e5d3739a2e1ea469cd87a4905684fbe64dac5a0e714f4737256c1a46642
Timestamp: 1710678935 Timestamp [UCT]: 2024-03-17 12:35:35 Age [y:d:h:m:s]: 00:342:18:36:00
Block: 980301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245031 RingCT/type: yes/0
Extra: 0105099e5d3739a2e1ea469cd87a4905684fbe64dac5a0e714f4737256c1a4664202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a49297b0cc50cc545f9c672dc60770db49a7e75bc4e67e181770044d4d5d4a5 0.600000000000 1440366 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": 980311, "vin": [ { "gen": { "height": 980301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a49297b0cc50cc545f9c672dc60770db49a7e75bc4e67e181770044d4d5d4a5" } } ], "extra": [ 1, 5, 9, 158, 93, 55, 57, 162, 225, 234, 70, 156, 216, 122, 73, 5, 104, 79, 190, 100, 218, 197, 160, 231, 20, 244, 115, 114, 86, 193, 164, 102, 66, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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