Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8996bdd0062f2f5a8233a48a7c79e6c9e5d3b18824fa2bd59e5f02f25a76d08

Tx prefix hash: a79836bf718dbfa4ea7d5630a584a04a24eb1ffbb7625d4442306128d969e676
Tx public key: dc7f58de049f8d75a349709c1f96b9ad461948e7147a627ea9a841859e55b864
Timestamp: 1737807476 Timestamp [UCT]: 2025-01-25 12:17:56 Age [y:d:h:m:s]: 00:048:03:44:18
Block: 1204994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34238 RingCT/type: yes/0
Extra: 01dc7f58de049f8d75a349709c1f96b9ad461948e7147a627ea9a841859e55b864021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f133149155a7f6e575bbdda10aeab5dad7c9f945fa977faf974bd2f4e9f3625c 0.600000000000 1691689 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": 1205004, "vin": [ { "gen": { "height": 1204994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f133149155a7f6e575bbdda10aeab5dad7c9f945fa977faf974bd2f4e9f3625c" } } ], "extra": [ 1, 220, 127, 88, 222, 4, 159, 141, 117, 163, 73, 112, 156, 31, 150, 185, 173, 70, 25, 72, 231, 20, 122, 98, 126, 169, 168, 65, 133, 158, 85, 184, 100, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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