Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47d66b79c467f79ebad71666ed4f163e20d515d430855e9aa55940f5cee39175

Tx prefix hash: 88122b877ff922b402206021ff45a047df16358cf412d35cde8071bf30da1f67
Tx public key: 5849c98f7edf8526dae91fcd8048e0dd5c2f3a80342bb3f7d95b2967236e30a5
Timestamp: 1699542948 Timestamp [UCT]: 2023-11-09 15:15:48 Age [y:d:h:m:s]: 01:131:01:51:06
Block: 887966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354873 RingCT/type: yes/0
Extra: 015849c98f7edf8526dae91fcd8048e0dd5c2f3a80342bb3f7d95b2967236e30a502110000000633af99f4000000000000000000

1 output(s) for total of 0.701132390000 dcy

stealth address amount amount idx
00: 756d2398c88ed66bb06ae704409f55a65f5b51231a54acac032b3f7796752c33 0.701132390000 1343879 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": 887976, "vin": [ { "gen": { "height": 887966 } } ], "vout": [ { "amount": 701132390, "target": { "key": "756d2398c88ed66bb06ae704409f55a65f5b51231a54acac032b3f7796752c33" } } ], "extra": [ 1, 88, 73, 201, 143, 126, 223, 133, 38, 218, 233, 31, 205, 128, 72, 224, 221, 92, 47, 58, 128, 52, 43, 179, 247, 217, 91, 41, 103, 35, 110, 48, 165, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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