Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f7ee33fccf8877394f17c557c828d6a3a93e6bd8bf1729182947040d66afa25

Tx prefix hash: 76cbdd7a8d8e2d80b72a8d12256692d2860edfd1fd8d50a5271f3d5a5efaa5a7
Tx public key: 445f76a412e548bfc3314c202f91dff1293e85a8576efb9468d5d5a5039dfd5e
Timestamp: 1707108051 Timestamp [UCT]: 2024-02-05 04:40:51 Age [y:d:h:m:s]: 01:087:15:39:35
Block: 950664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323718 RingCT/type: yes/0
Extra: 01445f76a412e548bfc3314c202f91dff1293e85a8576efb9468d5d5a5039dfd5e02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4e7dec59b0807276b24ce83304a65d75161ddee8bf966b68106e29f9ad523ee 0.600000000000 1409318 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": 950674, "vin": [ { "gen": { "height": 950664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4e7dec59b0807276b24ce83304a65d75161ddee8bf966b68106e29f9ad523ee" } } ], "extra": [ 1, 68, 95, 118, 164, 18, 229, 72, 191, 195, 49, 76, 32, 47, 145, 223, 241, 41, 62, 133, 168, 87, 110, 251, 148, 104, 213, 213, 165, 3, 157, 253, 94, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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