Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3917d70e2e863b694eb744472bd85fdd88a1447b9fb6046a3502226b3fd1849

Tx prefix hash: 1d5ee4b0045a467da2dea1c614282422db8cffe864b6b8df6e340c1e05061b75
Tx public key: 70283bb3e8765c96f6fa1cc1091aa27a618e1def0086ec73c67591ae6b579cc7
Timestamp: 1726351947 Timestamp [UCT]: 2024-09-14 22:12:27 Age [y:d:h:m:s]: 00:272:12:24:38
Block: 1110218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194566 RingCT/type: yes/0
Extra: 0170283bb3e8765c96f6fa1cc1091aa27a618e1def0086ec73c67591ae6b579cc7021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd7e8c8e263ff920641d5628329f9920cba9f605a957cc492518b4a8b4ec96f9 0.600000000000 1588743 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": 1110228, "vin": [ { "gen": { "height": 1110218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd7e8c8e263ff920641d5628329f9920cba9f605a957cc492518b4a8b4ec96f9" } } ], "extra": [ 1, 112, 40, 59, 179, 232, 118, 92, 150, 246, 250, 28, 193, 9, 26, 162, 122, 97, 142, 29, 239, 0, 134, 236, 115, 198, 117, 145, 174, 107, 87, 156, 199, 2, 17, 0, 0, 0, 6, 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