Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc5e252ecf79bb7b400cf30636b21227f652117fa86cd9b7189a4029be8bc7da

Tx prefix hash: e6d5a5c60315164e1a195e0818cbccf901d836e502fe291fbe3113d912ba7250
Tx public key: 8113e0ecc2dc92d01787313db20885c664d60b26692966d9b5f878f4666fae5c
Timestamp: 1620414527 Timestamp [UCT]: 2021-05-07 19:08:47 Age [y:d:h:m:s]: 03:195:03:05:55
Block: 256180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 899794 RingCT/type: yes/0
Extra: 018113e0ecc2dc92d01787313db20885c664d60b26692966d9b5f878f4666fae5c0211000002795ecf8729000000000000000000

1 output(s) for total of 86.930037207000 dcy

stealth address amount amount idx
00: 86f7583cc25c41db1c93dc7a6513fea0dbf0c932a8f4d7e4ab735b382f602152 86.930037207000 538875 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": 256190, "vin": [ { "gen": { "height": 256180 } } ], "vout": [ { "amount": 86930037207, "target": { "key": "86f7583cc25c41db1c93dc7a6513fea0dbf0c932a8f4d7e4ab735b382f602152" } } ], "extra": [ 1, 129, 19, 224, 236, 194, 220, 146, 208, 23, 135, 49, 61, 178, 8, 133, 198, 100, 214, 11, 38, 105, 41, 102, 217, 181, 248, 120, 244, 102, 111, 174, 92, 2, 17, 0, 0, 2, 121, 94, 207, 135, 41, 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