Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f09f66f52d20d42dcf5166b920c89d19439ac445614457346d16ffbf6e6d3d3

Tx prefix hash: 184c9c66d46b76f07ffe5a377bcb81a516028de77c893e8879eae16552111492
Tx public key: 8419b57aa5513d1aaffdc33fcbfde4a73329a5c9a92c84b67a4968fe61d1d6d6
Timestamp: 1738298622 Timestamp [UCT]: 2025-01-31 04:43:42 Age [y:d:h:m:s]: 00:136:05:02:41
Block: 1208838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97322 RingCT/type: yes/0
Extra: 018419b57aa5513d1aaffdc33fcbfde4a73329a5c9a92c84b67a4968fe61d1d6d60211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04a35dcb38882821a340e0cd514eace99a7b9e8631669c0da8f00390b8474d86 0.600000000000 1695573 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": 1208848, "vin": [ { "gen": { "height": 1208838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04a35dcb38882821a340e0cd514eace99a7b9e8631669c0da8f00390b8474d86" } } ], "extra": [ 1, 132, 25, 181, 122, 165, 81, 61, 26, 175, 253, 195, 63, 203, 253, 228, 167, 51, 41, 165, 201, 169, 44, 132, 182, 122, 73, 104, 254, 97, 209, 214, 214, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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