Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58ce316ad7a79e4670e5d0646be09cdc79cbb5f4e73fc2710530842f220bc4bd

Tx prefix hash: 83b6a54f8da896b8c1452f7e9142358fece5726273756468c973f10685d3e809
Tx public key: e503d5ab743cc46732648a022d146b9a11ab61258c35c12562e14488cb8edc1f
Timestamp: 1683684010 Timestamp [UCT]: 2023-05-10 02:00:10 Age [y:d:h:m:s]: 01:292:21:11:17
Block: 756734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470520 RingCT/type: yes/0
Extra: 01e503d5ab743cc46732648a022d146b9a11ab61258c35c12562e14488cb8edc1f021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.908210653000 dcy

stealth address amount amount idx
00: f99d9e85b4cec00b9cb38665012f0b40885de3d0ffc6ea31db99efe6d832b96d 1.908210653000 1205123 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": 756744, "vin": [ { "gen": { "height": 756734 } } ], "vout": [ { "amount": 1908210653, "target": { "key": "f99d9e85b4cec00b9cb38665012f0b40885de3d0ffc6ea31db99efe6d832b96d" } } ], "extra": [ 1, 229, 3, 213, 171, 116, 60, 196, 103, 50, 100, 138, 2, 45, 20, 107, 154, 17, 171, 97, 37, 140, 53, 193, 37, 98, 225, 68, 136, 203, 142, 220, 31, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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