Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f8ebe0b914cdbfa77f2dc515adb976a3eb0936a1634efb5867946880be79828

Tx prefix hash: 41b0d122a79271d6784e4b9e31b8804162f3a72a3818c0a83a6aae5a93d42955
Tx public key: fdd4e7b248e30b86bd5b3b466f91823b8df460a9e41014936edbf8371d579ccf
Timestamp: 1750680261 Timestamp [UCT]: 2025-06-23 12:04:21 Age [y:d:h:m:s]: 00:143:22:42:01
Block: 1311134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100759 RingCT/type: yes/0
Extra: 01fdd4e7b248e30b86bd5b3b466f91823b8df460a9e41014936edbf8371d579ccf02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6cc3e5a1b77fabcb04be66324edcc905ff749515dd79ca2f427b5a9f39f66f3 0.600000000000 1798759 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": 1311144, "vin": [ { "gen": { "height": 1311134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6cc3e5a1b77fabcb04be66324edcc905ff749515dd79ca2f427b5a9f39f66f3" } } ], "extra": [ 1, 253, 212, 231, 178, 72, 227, 11, 134, 189, 91, 59, 70, 111, 145, 130, 59, 141, 244, 96, 169, 228, 16, 20, 147, 110, 219, 248, 55, 29, 87, 156, 207, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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