Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81d0d825ea2602677a1a0f0516a10cefed73ac05ae5b0623d11ef0a6e0801068

Tx prefix hash: c679a5ef226362e5939d032fe4758fa2e1585008b8b1e9fe15f299adec9e6381
Tx public key: 0390f36210091692d6709d9601692f0a6ea7f94f99cd73f7d13b38a8da04cb1b
Timestamp: 1581197415 Timestamp [UCT]: 2020-02-08 21:30:15 Age [y:d:h:m:s]: 05:292:02:02:34
Block: 60923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1359232 RingCT/type: yes/0
Extra: 010390f36210091692d6709d9601692f0a6ea7f94f99cd73f7d13b38a8da04cb1b0211000000034943cd9f000000000000000000

1 output(s) for total of 385.600534864000 dcy

stealth address amount amount idx
00: b05082217356aec95751a05ee4cfc8407a4be4dda5552027cd06a213548037e7 385.600534864000 112302 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": 60933, "vin": [ { "gen": { "height": 60923 } } ], "vout": [ { "amount": 385600534864, "target": { "key": "b05082217356aec95751a05ee4cfc8407a4be4dda5552027cd06a213548037e7" } } ], "extra": [ 1, 3, 144, 243, 98, 16, 9, 22, 146, 214, 112, 157, 150, 1, 105, 47, 10, 110, 167, 249, 79, 153, 205, 115, 247, 209, 59, 56, 168, 218, 4, 203, 27, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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