Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f4899b395750fd6cfcbc2c6e04cc43c091266669da6a1e9235d7ca8c82913bc

Tx prefix hash: 2cff8737ca1a57f65e7f9c916c36d9d85a7cf96b440470f8f2e103b9f883e4ec
Tx public key: 2c940ef5cea1cf84bbbb14b0f8dad5dc0c7ea601ff1a0de453c019753149b81e
Timestamp: 1658870573 Timestamp [UCT]: 2022-07-26 21:22:53 Age [y:d:h:m:s]: 02:174:07:18:37
Block: 552370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645991 RingCT/type: yes/0
Extra: 012c940ef5cea1cf84bbbb14b0f8dad5dc0c7ea601ff1a0de453c019753149b81e021100000001ec6d1a1a000000000000000000

1 output(s) for total of 9.073378313000 dcy

stealth address amount amount idx
00: d90a2ea9352625f9a84f990cb710b5c7550023da12092ec9f001d93145ba830f 9.073378313000 984072 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": 552380, "vin": [ { "gen": { "height": 552370 } } ], "vout": [ { "amount": 9073378313, "target": { "key": "d90a2ea9352625f9a84f990cb710b5c7550023da12092ec9f001d93145ba830f" } } ], "extra": [ 1, 44, 148, 14, 245, 206, 161, 207, 132, 187, 187, 20, 176, 248, 218, 213, 220, 12, 126, 166, 1, 255, 26, 13, 228, 83, 192, 25, 117, 49, 73, 184, 30, 2, 17, 0, 0, 0, 1, 236, 109, 26, 26, 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