Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5f02da34dc63a26b07e295c27bb9c60cc5b4213ae461f7298c865548050332f

Tx prefix hash: 5c7a57e7086d5c4ada3195a21f5cb5a587c5f77e47926937e611d2af289bb538
Tx public key: bf6955f41602692a8c49b6e292d040ee2bc1d59447f05abf7df2d0bcf4fc8ca5
Timestamp: 1705622167 Timestamp [UCT]: 2024-01-18 23:56:07 Age [y:d:h:m:s]: 01:149:02:57:24
Block: 938337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367632 RingCT/type: yes/0
Extra: 01bf6955f41602692a8c49b6e292d040ee2bc1d59447f05abf7df2d0bcf4fc8ca502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c27c5ba5913a7a95c581d9dff07fe4ab0cbef3a70aec5f0e9dd7723e5d9f5fd 0.600000000000 1396407 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": 938347, "vin": [ { "gen": { "height": 938337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c27c5ba5913a7a95c581d9dff07fe4ab0cbef3a70aec5f0e9dd7723e5d9f5fd" } } ], "extra": [ 1, 191, 105, 85, 244, 22, 2, 105, 42, 140, 73, 182, 226, 146, 208, 64, 238, 43, 193, 213, 148, 71, 240, 90, 191, 125, 242, 208, 188, 244, 252, 140, 165, 2, 17, 0, 0, 0, 2, 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