Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb99ba9e6656cd1c88d8fa9e86c140885df92c7cf7e0db47d4a55d07760c3655

Tx prefix hash: dd550605b655d07041b5e9a2f27789bbec629afdf080ea2dc954bbd82783bfa8
Tx public key: f4cc37de2b3dcd7eb38b12f22a20f8cea64a3bbec3182c42b5fc0cd2e3d24c8a
Timestamp: 1657053008 Timestamp [UCT]: 2022-07-05 20:30:08 Age [y:d:h:m:s]: 02:312:01:45:17
Block: 537414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 744182 RingCT/type: yes/0
Extra: 01f4cc37de2b3dcd7eb38b12f22a20f8cea64a3bbec3182c42b5fc0cd2e3d24c8a02110000001c4da16a3a000000000000000000

1 output(s) for total of 10.170082538000 dcy

stealth address amount amount idx
00: 3955d8d4f439d1d9ec53301b6d2d15a2b1be9be133fea48c2ff65a1f040dabb2 10.170082538000 967301 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": 537424, "vin": [ { "gen": { "height": 537414 } } ], "vout": [ { "amount": 10170082538, "target": { "key": "3955d8d4f439d1d9ec53301b6d2d15a2b1be9be133fea48c2ff65a1f040dabb2" } } ], "extra": [ 1, 244, 204, 55, 222, 43, 61, 205, 126, 179, 139, 18, 242, 42, 32, 248, 206, 166, 74, 59, 190, 195, 24, 44, 66, 181, 252, 12, 210, 227, 210, 76, 138, 2, 17, 0, 0, 0, 28, 77, 161, 106, 58, 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