Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4be0776fd03425cdc159072aecc14960f534e7b13c580b56cd053d1d8a95043c

Tx prefix hash: 6c03302fbf9892ab868f2d3b0b03dc225617bf21b53d5eda5f342676b4694b65
Tx public key: 1ebdb5c7826e75df1c72779d6630aa363ad3e447ca5605c019b931274c834fc0
Timestamp: 1713708777 Timestamp [UCT]: 2024-04-21 14:12:57 Age [y:d:h:m:s]: 00:352:21:27:39
Block: 1005394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252289 RingCT/type: yes/0
Extra: 011ebdb5c7826e75df1c72779d6630aa363ad3e447ca5605c019b931274c834fc00211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f0d6e896e67109527f22a0101fae2c299cf9d83fb693cf47a8fafb5ce61a828 0.600000000000 1466046 of 15

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": 1005404, "vin": [ { "gen": { "height": 1005394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f0d6e896e67109527f22a0101fae2c299cf9d83fb693cf47a8fafb5ce61a828" } } ], "extra": [ 1, 30, 189, 181, 199, 130, 110, 117, 223, 28, 114, 119, 157, 102, 48, 170, 54, 58, 211, 228, 71, 202, 86, 5, 192, 25, 185, 49, 39, 76, 131, 79, 192, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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