Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b841140c23b92de2db0a6c61cbc62861de1c7097ca39cf6b60bc2303f02cdeb

Tx prefix hash: 4f4e743148ad0ea149885d336b31b2c1023d14cddeae996a1b38e72ce9acbad3
Tx public key: fa2a3af17873d8c77c4135cc0ea8dfc3f31a9de9245fab05ce7b3ec4aae86f3a
Timestamp: 1694548149 Timestamp [UCT]: 2023-09-12 19:49:09 Age [y:d:h:m:s]: 01:075:06:25:24
Block: 846727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315090 RingCT/type: yes/0
Extra: 01fa2a3af17873d8c77c4135cc0ea8dfc3f31a9de9245fab05ce7b3ec4aae86f3a02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.960377590000 dcy

stealth address amount amount idx
00: a63310007f4ec0ebc2d004f3c0c9c63dfe771b528a93361471f481ce5fdbf2a6 0.960377590000 1300207 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": 846737, "vin": [ { "gen": { "height": 846727 } } ], "vout": [ { "amount": 960377590, "target": { "key": "a63310007f4ec0ebc2d004f3c0c9c63dfe771b528a93361471f481ce5fdbf2a6" } } ], "extra": [ 1, 250, 42, 58, 241, 120, 115, 216, 199, 124, 65, 53, 204, 14, 168, 223, 195, 243, 26, 157, 233, 36, 95, 171, 5, 206, 123, 62, 196, 170, 232, 111, 58, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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