Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f4ad9f3d7f7fa6e02de9f2fdd82caec3c5270270cee533318afaff0d0e5c7a1

Tx prefix hash: bc507bd2095c6188a7d01eb4eb0e4d2a064df976bf81449f1624d67d3293f9e5
Tx public key: 8d17362c17bc3a4e86babdbb37cf39880b11b656d6bf7026b99ac8ec5885b6b3
Timestamp: 1576643226 Timestamp [UCT]: 2019-12-18 04:27:06 Age [y:d:h:m:s]: 05:010:18:36:07
Block: 28101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155789 RingCT/type: yes/0
Extra: 018d17362c17bc3a4e86babdbb37cf39880b11b656d6bf7026b99ac8ec5885b6b30211000000119159db1e000000000000000000

1 output(s) for total of 495.325386158000 dcy

stealth address amount amount idx
00: 98c022a10cda568e79d7a5e7d2fc94eef941b928dc524425d5c85802c8ff65a2 495.325386158000 46623 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": 28111, "vin": [ { "gen": { "height": 28101 } } ], "vout": [ { "amount": 495325386158, "target": { "key": "98c022a10cda568e79d7a5e7d2fc94eef941b928dc524425d5c85802c8ff65a2" } } ], "extra": [ 1, 141, 23, 54, 44, 23, 188, 58, 78, 134, 186, 189, 187, 55, 207, 57, 136, 11, 17, 182, 86, 214, 191, 112, 38, 185, 154, 200, 236, 88, 133, 182, 179, 2, 17, 0, 0, 0, 17, 145, 89, 219, 30, 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