Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6db3cd5c48f18ea5893d981c1db622cdc8db1d647c0b205c255dbc71b2b56633

Tx prefix hash: ea8a20238430659395897d7e312930815fad4d6ffce3aabfb28657951e128eec
Tx public key: c1f59349609df86cfafdf891b3ff95bead3ea6979445dc5b4d83867ebd29b903
Timestamp: 1581907497 Timestamp [UCT]: 2020-02-17 02:44:57 Age [y:d:h:m:s]: 04:323:08:31:11
Block: 66487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123502 RingCT/type: yes/0
Extra: 01c1f59349609df86cfafdf891b3ff95bead3ea6979445dc5b4d83867ebd29b90302110000000cd81c26c0000000000000000000

1 output(s) for total of 369.580702568000 dcy

stealth address amount amount idx
00: 4d73ac1ef7c1678d9e8a94a4dd557b1d5a44959a69e2659d58f63d75bcf86549 369.580702568000 122472 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": 66497, "vin": [ { "gen": { "height": 66487 } } ], "vout": [ { "amount": 369580702568, "target": { "key": "4d73ac1ef7c1678d9e8a94a4dd557b1d5a44959a69e2659d58f63d75bcf86549" } } ], "extra": [ 1, 193, 245, 147, 73, 96, 157, 248, 108, 250, 253, 248, 145, 179, 255, 149, 190, 173, 62, 166, 151, 148, 69, 220, 91, 77, 131, 134, 126, 189, 41, 185, 3, 2, 17, 0, 0, 0, 12, 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