Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7c9bbaaa20773bcc3cbacceda7c56a08adaaff787ec343f09635e6555948ad6

Tx prefix hash: 1101ff281742c35bdc75b68b38a102b9da0e8036b07ddac89e410ef2f24341eb
Tx public key: a5e5dbc77d98d6bff815cb1f06965e919439e084b2722ca8781cdd512c83fbaa
Timestamp: 1674771257 Timestamp [UCT]: 2023-01-26 22:14:17 Age [y:d:h:m:s]: 02:286:04:56:44
Block: 683469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 723904 RingCT/type: yes/0
Extra: 01a5e5dbc77d98d6bff815cb1f06965e919439e084b2722ca8781cdd512c83fbaa021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.337209099000 dcy

stealth address amount amount idx
00: 86f283cce35fe8699dbe0663e1d02d17a95e71970a268cd4dbb85a8723183c29 3.337209099000 1125658 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": 683479, "vin": [ { "gen": { "height": 683469 } } ], "vout": [ { "amount": 3337209099, "target": { "key": "86f283cce35fe8699dbe0663e1d02d17a95e71970a268cd4dbb85a8723183c29" } } ], "extra": [ 1, 165, 229, 219, 199, 125, 152, 214, 191, 248, 21, 203, 31, 6, 150, 94, 145, 148, 57, 224, 132, 178, 114, 44, 168, 120, 28, 221, 81, 44, 131, 251, 170, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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