Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60f78cb80d668c83c83d6b7f3ff858b2ab526a7f6896f2272f49d60a77600b53

Tx prefix hash: e6a47afdf3c66cde4ac96e2c42d8961095c6817cfed7a3c5a44ee1bfa821ac0d
Tx public key: 4202545fdc61fde6b10546f939729964c56fc37a6af73d1fd281e8ffbde747b4
Timestamp: 1578434950 Timestamp [UCT]: 2020-01-07 22:09:10 Age [y:d:h:m:s]: 04:324:10:33:25
Block: 40804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121202 RingCT/type: yes/0
Extra: 014202545fdc61fde6b10546f939729964c56fc37a6af73d1fd281e8ffbde747b4021100000008d81c26c0000000000000000000

1 output(s) for total of 449.573036214000 dcy

stealth address amount amount idx
00: 83b16adceed897d8f6b24ca23a3c734bf1a72c068dff23fc4f75b4df5569db4f 449.573036214000 72016 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": 40814, "vin": [ { "gen": { "height": 40804 } } ], "vout": [ { "amount": 449573036214, "target": { "key": "83b16adceed897d8f6b24ca23a3c734bf1a72c068dff23fc4f75b4df5569db4f" } } ], "extra": [ 1, 66, 2, 84, 95, 220, 97, 253, 230, 177, 5, 70, 249, 57, 114, 153, 100, 197, 111, 195, 122, 106, 247, 61, 31, 210, 129, 232, 255, 189, 231, 71, 180, 2, 17, 0, 0, 0, 8, 216, 28, 38, 192, 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