Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 383de1969f7c32341009e0c560ead735d041723116f81366218e9da96491d9e1

Tx prefix hash: 651c171f7832fb23eee48970ee036941566b5c3ff89bd9271cd887d3cfdb36dc
Tx public key: 3dc76bd6e9d34caceb94a41858fa89c5b6fc6a8d2c39a9e0aa9bca426ae57006
Timestamp: 1710717173 Timestamp [UCT]: 2024-03-17 23:12:53 Age [y:d:h:m:s]: 01:078:06:56:03
Block: 980617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316964 RingCT/type: yes/0
Extra: 013dc76bd6e9d34caceb94a41858fa89c5b6fc6a8d2c39a9e0aa9bca426ae5700602110000002259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f596ebc342eb27701ef8a82ec07cfc2230d6ac60af98ded18d2cbbc0bab1b95 0.600000000000 1440696 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": 980627, "vin": [ { "gen": { "height": 980617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f596ebc342eb27701ef8a82ec07cfc2230d6ac60af98ded18d2cbbc0bab1b95" } } ], "extra": [ 1, 61, 199, 107, 214, 233, 211, 76, 172, 235, 148, 164, 24, 88, 250, 137, 197, 182, 252, 106, 141, 44, 57, 169, 224, 170, 155, 202, 66, 106, 229, 112, 6, 2, 17, 0, 0, 0, 34, 89, 218, 211, 245, 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