Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31e6a39f7d9d90081915e840ef57fe6d1fbc4e221602fd3516cc7718b8318414

Tx prefix hash: 223ccd0fe468aba9bacef48d99b7e05b60bd9b3343004ba8323a76969d3be53b
Tx public key: 06fda274f17329af63d85bd50a8e79c8fca2261af942aed56716db1dc81d1fae
Timestamp: 1700846947 Timestamp [UCT]: 2023-11-24 17:29:07 Age [y:d:h:m:s]: 01:097:05:27:52
Block: 898766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330622 RingCT/type: yes/0
Extra: 0106fda274f17329af63d85bd50a8e79c8fca2261af942aed56716db1dc81d1fae0211000000014b8f5122000000000000000000

1 output(s) for total of 0.645676725000 dcy

stealth address amount amount idx
00: e0dae20df60887dfe4aa8ba03717679d1a5852331d41ca183dc6c5069fe3fbf7 0.645676725000 1355201 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": 898776, "vin": [ { "gen": { "height": 898766 } } ], "vout": [ { "amount": 645676725, "target": { "key": "e0dae20df60887dfe4aa8ba03717679d1a5852331d41ca183dc6c5069fe3fbf7" } } ], "extra": [ 1, 6, 253, 162, 116, 241, 115, 41, 175, 99, 216, 91, 213, 10, 142, 121, 200, 252, 162, 38, 26, 249, 66, 174, 213, 103, 22, 219, 29, 200, 29, 31, 174, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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