Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1779cbbe4d5c68605e953d82065ebe64a57f83f4d21782c6ccc3c12a852cf38c

Tx prefix hash: ca433e2186ef0fd4c29c414cd0754c16ea9e377f4a9445c81bc37d9340d0611e
Tx public key: 78dcf2bbfacb5775666e3d788112fa247ac32324c7a80e271b3f2760ce4231f4
Timestamp: 1578323881 Timestamp [UCT]: 2020-01-06 15:18:01 Age [y:d:h:m:s]: 05:130:18:09:57
Block: 39761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1243601 RingCT/type: yes/0
Extra: 0178dcf2bbfacb5775666e3d788112fa247ac32324c7a80e271b3f2760ce4231f40211000000152264afe6000000000000000000

1 output(s) for total of 453.174600317000 dcy

stealth address amount amount idx
00: dc1255a3130fdd757085f56e126699d80bb2a691eff0c9f137c9aec29944dfe9 453.174600317000 69049 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": 39771, "vin": [ { "gen": { "height": 39761 } } ], "vout": [ { "amount": 453174600317, "target": { "key": "dc1255a3130fdd757085f56e126699d80bb2a691eff0c9f137c9aec29944dfe9" } } ], "extra": [ 1, 120, 220, 242, 187, 250, 203, 87, 117, 102, 110, 61, 120, 129, 18, 250, 36, 122, 195, 35, 36, 199, 168, 14, 39, 27, 63, 39, 96, 206, 66, 49, 244, 2, 17, 0, 0, 0, 21, 34, 100, 175, 230, 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