Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cd0d5eb108f61c5f9eccc88b3cfbb3dccdb31416bb4f908ee259076020b79c7

Tx prefix hash: 981158c826d05aeaf848391d3e6d056ec6b11e5f6420a0af0055f947067f739f
Tx public key: 0c94232aa71a228f859ab39d41bf0eea739556ce9bf63f84b34d9e8f5920d507
Timestamp: 1701968691 Timestamp [UCT]: 2023-12-07 17:04:51 Age [y:d:h:m:s]: 01:132:09:10:55
Block: 908069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355759 RingCT/type: yes/0
Extra: 010c94232aa71a228f859ab39d41bf0eea739556ce9bf63f84b34d9e8f5920d507021100000001faf35c9c000000000000000000

1 output(s) for total of 0.601437381000 dcy

stealth address amount amount idx
00: da6e3ac136f6998f57def062095a20ba7b214b23c75a1ecdfe557e52bf0b5af8 0.601437381000 1365080 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": 908079, "vin": [ { "gen": { "height": 908069 } } ], "vout": [ { "amount": 601437381, "target": { "key": "da6e3ac136f6998f57def062095a20ba7b214b23c75a1ecdfe557e52bf0b5af8" } } ], "extra": [ 1, 12, 148, 35, 42, 167, 26, 34, 143, 133, 154, 179, 157, 65, 191, 14, 234, 115, 149, 86, 206, 155, 246, 63, 132, 179, 77, 158, 143, 89, 32, 213, 7, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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