Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd929158a92acf4031fa1b51698c9aaade6d773670c960e883f617b17c7e4c99

Tx prefix hash: 64c1b54c9e2b3e58d6ef607e6a4188862bff5cd73fd483ff519fcbb48f410425
Tx public key: 431136482e0719c3c60b944dad6a69b353daf341eba3eb2424d3c6d6dfb4684b
Timestamp: 1700496160 Timestamp [UCT]: 2023-11-20 16:02:40 Age [y:d:h:m:s]: 01:175:12:27:24
Block: 895859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386642 RingCT/type: yes/0
Extra: 01431136482e0719c3c60b944dad6a69b353daf341eba3eb2424d3c6d6dfb4684b021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.660157001000 dcy

stealth address amount amount idx
00: 0e61abb8334f8f4fdd6671a41779af977c656e46235d13628a1b4d1994de4833 0.660157001000 1352106 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": 895869, "vin": [ { "gen": { "height": 895859 } } ], "vout": [ { "amount": 660157001, "target": { "key": "0e61abb8334f8f4fdd6671a41779af977c656e46235d13628a1b4d1994de4833" } } ], "extra": [ 1, 67, 17, 54, 72, 46, 7, 25, 195, 198, 11, 148, 77, 173, 106, 105, 179, 83, 218, 243, 65, 235, 163, 235, 36, 36, 211, 198, 214, 223, 180, 104, 75, 2, 17, 0, 0, 0, 6, 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