Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cbf0ab1d27d175e87815f2567353a3d1f993e1c6edd07cf39390fe0524118ff

Tx prefix hash: 77666a8655e73fd768e2c026199f5a1f08178409bfd1bc2de983c4f0ee0d32b4
Tx public key: 50675f812942c45f2b8bbdf8f7105fe9c40c1bd7e7415063b535e685311382b0
Timestamp: 1579124967 Timestamp [UCT]: 2020-01-15 21:49:27 Age [y:d:h:m:s]: 04:347:08:36:18
Block: 46314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137801 RingCT/type: yes/0
Extra: 0150675f812942c45f2b8bbdf8f7105fe9c40c1bd7e7415063b535e685311382b00211000000074943cd9f000000000000000000

1 output(s) for total of 431.065564230000 dcy

stealth address amount amount idx
00: ac84d0143ec6d904c5dd38b6ee8d1b58abc714da3c43558f82886f3234faecb6 431.065564230000 85128 of 0

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": 46324, "vin": [ { "gen": { "height": 46314 } } ], "vout": [ { "amount": 431065564230, "target": { "key": "ac84d0143ec6d904c5dd38b6ee8d1b58abc714da3c43558f82886f3234faecb6" } } ], "extra": [ 1, 80, 103, 95, 129, 41, 66, 196, 95, 43, 139, 189, 248, 247, 16, 95, 233, 196, 12, 27, 215, 231, 65, 80, 99, 181, 53, 230, 133, 49, 19, 130, 176, 2, 17, 0, 0, 0, 7, 73, 67, 205, 159, 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