Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0441f2fc9f5782e1ef321712d1998bfa4fce49646ce5cb8352f93b799d73c8a

Tx prefix hash: 65ef319520d35b4d9b1a2c70cfbd2fe8adc97581b9c53a2fec3f2299ae2348b6
Tx public key: 0a787894d0f2a0fec634368e9bbce7065936bf8af5ee2840118486a99db1ad44
Timestamp: 1636724545 Timestamp [UCT]: 2021-11-12 13:42:25 Age [y:d:h:m:s]: 03:354:08:46:12
Block: 372840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1029384 RingCT/type: yes/0
Extra: 010a787894d0f2a0fec634368e9bbce7065936bf8af5ee2840118486a99db1ad4402110000001a4f792ffd000000000000000000

1 output(s) for total of 35.697207187000 dcy

stealth address amount amount idx
00: 68ca09e79ef90aa63ff433aeebeeef5a42c355bdd43d4922b2e81d4e4ea9e2c0 35.697207187000 755156 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": 372850, "vin": [ { "gen": { "height": 372840 } } ], "vout": [ { "amount": 35697207187, "target": { "key": "68ca09e79ef90aa63ff433aeebeeef5a42c355bdd43d4922b2e81d4e4ea9e2c0" } } ], "extra": [ 1, 10, 120, 120, 148, 208, 242, 160, 254, 198, 52, 54, 142, 155, 188, 231, 6, 89, 54, 191, 138, 245, 238, 40, 64, 17, 132, 134, 169, 157, 177, 173, 68, 2, 17, 0, 0, 0, 26, 79, 121, 47, 253, 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