Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d644131f29d6b9926b1fc30cc0f1dec954bf14875be80e26be54acc21b2502b6

Tx prefix hash: d0ab69ff9a2ba54ad90c270ccd9b46f828e2cdd6bff778c38cc4e4c92eda1f17
Tx public key: 887836f3c61d62d4cb3212b718dc9270b5bb491a7579cd675bd3c2f3def40e7b
Timestamp: 1739745995 Timestamp [UCT]: 2025-02-16 22:46:35 Age [y:d:h:m:s]: 00:233:23:58:00
Block: 1220784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164965 RingCT/type: yes/0
Extra: 01887836f3c61d62d4cb3212b718dc9270b5bb491a7579cd675bd3c2f3def40e7b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee0c45fdddc9a5d9df3820694cad0ac47344027f331006ec7f636675a37f882c 0.600000000000 1707625 of 15

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": 1220794, "vin": [ { "gen": { "height": 1220784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee0c45fdddc9a5d9df3820694cad0ac47344027f331006ec7f636675a37f882c" } } ], "extra": [ 1, 136, 120, 54, 243, 198, 29, 98, 212, 203, 50, 18, 183, 24, 220, 146, 112, 181, 187, 73, 26, 117, 121, 205, 103, 91, 211, 194, 243, 222, 244, 14, 123, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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