Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3044bdd9d9f72957622a919154b4dce6788d163be30a285e2ace7659ff9f6e33

Tx prefix hash: f0a2865f637cfc635560199c40cf8eb2200e9845fa93544b59bea6233e4f1db2
Tx public key: 311ee67fb9b4f0101deb95665c2c55a436f1f81d50a543b1b502e080c1a834fa
Timestamp: 1718215727 Timestamp [UCT]: 2024-06-12 18:08:47 Age [y:d:h:m:s]: 01:001:09:57:21
Block: 1042763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261821 RingCT/type: yes/0
Extra: 01311ee67fb9b4f0101deb95665c2c55a436f1f81d50a543b1b502e080c1a834fa0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2e96f038fd4fe82ba71191bbb8359a49778fd2a0738c5816a2e309d786c079f 0.600000000000 1511758 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": 1042773, "vin": [ { "gen": { "height": 1042763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2e96f038fd4fe82ba71191bbb8359a49778fd2a0738c5816a2e309d786c079f" } } ], "extra": [ 1, 49, 30, 230, 127, 185, 180, 240, 16, 29, 235, 149, 102, 92, 44, 85, 164, 54, 241, 248, 29, 80, 165, 67, 177, 181, 2, 224, 128, 193, 168, 52, 250, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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