Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c0ff10f8b58a8b2f598034f0505d29c454199a5fba78cdd9e6f39cb664a2878

Tx prefix hash: df07cab07af1b55b2bf6d73a062cef3b8fea1c7f241f9dc7b76414967a9a7478
Tx public key: 177514473dfd31911a17051b063c12d6a10206ebe1eb8fa32ea1509db368f2ce
Timestamp: 1724805559 Timestamp [UCT]: 2024-08-28 00:39:19 Age [y:d:h:m:s]: 00:254:10:27:27
Block: 1097389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181722 RingCT/type: yes/0
Extra: 01177514473dfd31911a17051b063c12d6a10206ebe1eb8fa32ea1509db368f2ce021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc3cc4d0c7c636872b1e78358953b8b44f56d0180ab9cf47206ed6bce2364979 0.600000000000 1572784 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": 1097399, "vin": [ { "gen": { "height": 1097389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc3cc4d0c7c636872b1e78358953b8b44f56d0180ab9cf47206ed6bce2364979" } } ], "extra": [ 1, 23, 117, 20, 71, 61, 253, 49, 145, 26, 23, 5, 27, 6, 60, 18, 214, 161, 2, 6, 235, 225, 235, 143, 163, 46, 161, 80, 157, 179, 104, 242, 206, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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