Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8adf56810b406087adf2907a590e0cd313417a03b7d1d168846d674cfaada51c

Tx prefix hash: a0d8b776eedfb3eecf93e66f4530249db5f687e829e0667185cfdfb93bc00ed6
Tx public key: 09d7f98486e66b1bc3146c997fc8bbd55cd32724e6a451ca1c9d5e3e919f1371
Timestamp: 1736120116 Timestamp [UCT]: 2025-01-05 23:35:16 Age [y:d:h:m:s]: 00:094:23:27:13
Block: 1191069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67657 RingCT/type: yes/0
Extra: 0109d7f98486e66b1bc3146c997fc8bbd55cd32724e6a451ca1c9d5e3e919f137102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56af2e2dff570b7719662f9fa413c8d21bc42d06a1e873bf1b55c913aeb41aff 0.600000000000 1677592 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": 1191079, "vin": [ { "gen": { "height": 1191069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56af2e2dff570b7719662f9fa413c8d21bc42d06a1e873bf1b55c913aeb41aff" } } ], "extra": [ 1, 9, 215, 249, 132, 134, 230, 107, 27, 195, 20, 108, 153, 127, 200, 187, 213, 92, 211, 39, 36, 230, 164, 81, 202, 28, 157, 94, 62, 145, 159, 19, 113, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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