Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa75d6ab8f867ccf0b2b76ef8b3524ea3bfe8dfb143070f5c9e5d82bb07808c

Tx prefix hash: e36bca61cd2a2c8c548a3d36910f9ceb6f2df03044be3f4e0c0a2e85a8847be8
Tx public key: 6a57076ce5d01369f268dc33b032c1ee5c7cfb11e41f9586d5810f85ddf9a07e
Timestamp: 1724847966 Timestamp [UCT]: 2024-08-28 12:26:06 Age [y:d:h:m:s]: 00:237:01:22:40
Block: 1097743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169301 RingCT/type: yes/0
Extra: 016a57076ce5d01369f268dc33b032c1ee5c7cfb11e41f9586d5810f85ddf9a07e02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36e14e5e819bd5416a4460c47f41df8f65424f673a65bbf2857bbfb6211980d2 0.600000000000 1573218 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": 1097753, "vin": [ { "gen": { "height": 1097743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36e14e5e819bd5416a4460c47f41df8f65424f673a65bbf2857bbfb6211980d2" } } ], "extra": [ 1, 106, 87, 7, 108, 229, 208, 19, 105, 242, 104, 220, 51, 176, 50, 193, 238, 92, 124, 251, 17, 228, 31, 149, 134, 213, 129, 15, 133, 221, 249, 160, 126, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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