Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b33301411f3d8dee3caf98e4e1610e9a1e6f9ede1b7d672f7b5bc56db0250f4e

Tx prefix hash: 42782f2fe207df1f15034bf9e98d2ffacaa32f1df09c03d44a6cfc15875269f7
Tx public key: 6ba0ba254aa17f98a84336f44c5561451dd5b4996d1e1b5034e157ff9530198e
Timestamp: 1644724497 Timestamp [UCT]: 2022-02-13 03:54:57 Age [y:d:h:m:s]: 03:091:07:50:15
Block: 437467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 845249 RingCT/type: yes/0
Extra: 016ba0ba254aa17f98a84336f44c5561451dd5b4996d1e1b5034e157ff9530198e0211000000074a0f5013000000000000000000

1 output(s) for total of 21.801708316000 dcy

stealth address amount amount idx
00: c89cde9fc25e98a9a95f4f54542fd579317f595a011d3d32d961e75968f59bbf 21.801708316000 849104 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": 437477, "vin": [ { "gen": { "height": 437467 } } ], "vout": [ { "amount": 21801708316, "target": { "key": "c89cde9fc25e98a9a95f4f54542fd579317f595a011d3d32d961e75968f59bbf" } } ], "extra": [ 1, 107, 160, 186, 37, 74, 161, 127, 152, 168, 67, 54, 244, 76, 85, 97, 69, 29, 213, 180, 153, 109, 30, 27, 80, 52, 225, 87, 255, 149, 48, 25, 142, 2, 17, 0, 0, 0, 7, 74, 15, 80, 19, 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