Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2c6d06f9e9f0e0e747ef40bcee68b74a6632b6d3000c1089394146e954dbc54

Tx prefix hash: 57d7689cbc6ec6feaa8e9decbd63b666c470dfa5cdd58314c51f3c8b999aec14
Tx public key: be506a4adcce01f7a1ab74c5735bf949ef4042def4f2f046f944878e1069df71
Timestamp: 1580888541 Timestamp [UCT]: 2020-02-05 07:42:21 Age [y:d:h:m:s]: 04:275:16:05:03
Block: 59044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1088369 RingCT/type: yes/0
Extra: 01be506a4adcce01f7a1ab74c5735bf949ef4042def4f2f046f944878e1069df71021100000001ff58ae94000000000000000000

1 output(s) for total of 391.168196217000 dcy

stealth address amount amount idx
00: f8cedc7eda4019e12da14b6c573c6b29d771d5b0212a4342a3705880c66d8eaf 391.168196217000 109030 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": 59054, "vin": [ { "gen": { "height": 59044 } } ], "vout": [ { "amount": 391168196217, "target": { "key": "f8cedc7eda4019e12da14b6c573c6b29d771d5b0212a4342a3705880c66d8eaf" } } ], "extra": [ 1, 190, 80, 106, 74, 220, 206, 1, 247, 161, 171, 116, 197, 115, 91, 249, 73, 239, 64, 66, 222, 244, 242, 240, 70, 249, 68, 135, 142, 16, 105, 223, 113, 2, 17, 0, 0, 0, 1, 255, 88, 174, 148, 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