Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90a153e317b3e93ef4090db15433623a29ea4399d71ae63306469b93e97d1b18

Tx prefix hash: 490fa41d60ec47883dc494be3e0a66f4ba2c5bc1e2f7fd1569de926a2d997889
Tx public key: 67d05b490eef28e08dcc236dcebba8d007c63c726fbec8ad625a144bb72f6bd1
Timestamp: 1714340719 Timestamp [UCT]: 2024-04-28 21:45:19 Age [y:d:h:m:s]: 00:275:02:18:04
Block: 1010631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196642 RingCT/type: yes/0
Extra: 0167d05b490eef28e08dcc236dcebba8d007c63c726fbec8ad625a144bb72f6bd102110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 765962da2b03755905d6fb83e1cfb30b6fab6e6b067428be530d1e9a8ac6d27d 0.600000000000 1472641 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": 1010641, "vin": [ { "gen": { "height": 1010631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "765962da2b03755905d6fb83e1cfb30b6fab6e6b067428be530d1e9a8ac6d27d" } } ], "extra": [ 1, 103, 208, 91, 73, 14, 239, 40, 224, 141, 204, 35, 109, 206, 187, 168, 208, 7, 198, 60, 114, 111, 190, 200, 173, 98, 90, 20, 75, 183, 47, 107, 209, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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