Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0767a95e5193682a09542534e119f4c165df5913338ef0a34ce71cdb060911eb

Tx prefix hash: 8d08fa5db20a3fe6f7871f84051bdeed1f75d51f0254738303cbbec11425022e
Tx public key: 784ee555bcba1691bea6de9c3c9542759c9fb4bd81b3aab9a4be3e9b2a7350a1
Timestamp: 1719535874 Timestamp [UCT]: 2024-06-28 00:51:14 Age [y:d:h:m:s]: 00:269:21:06:19
Block: 1053707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192823 RingCT/type: yes/0
Extra: 01784ee555bcba1691bea6de9c3c9542759c9fb4bd81b3aab9a4be3e9b2a7350a10211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ff5c693c9b0926a444a4e1fe1f145effd3ef2073ebf8a008da138fedee612d0 0.600000000000 1524056 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": 1053717, "vin": [ { "gen": { "height": 1053707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ff5c693c9b0926a444a4e1fe1f145effd3ef2073ebf8a008da138fedee612d0" } } ], "extra": [ 1, 120, 78, 229, 85, 188, 186, 22, 145, 190, 166, 222, 156, 60, 149, 66, 117, 156, 159, 180, 189, 129, 179, 170, 185, 164, 190, 62, 155, 42, 115, 80, 161, 2, 17, 0, 0, 0, 6, 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