Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd710459a5cdc9e67b428445c560b344dc2d8208dafc35470f03dfbbe286c8de

Tx prefix hash: 7d612d2544e675910763e5f727cd85199e6bc835c33ba0e6b80c2e4362e9b7ed
Tx public key: fa4915120567a36fdd35f431329f6a2cfca6a5156d0ece2fcf8d88f99e34e5d7
Timestamp: 1750996427 Timestamp [UCT]: 2025-06-27 03:53:47 Age [y:d:h:m:s]: 00:147:13:01:28
Block: 1313612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103467 RingCT/type: yes/0
Extra: 01fa4915120567a36fdd35f431329f6a2cfca6a5156d0ece2fcf8d88f99e34e5d7021100000007bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 015a9b42b4e25a97325c6225c0fd82c5c266cec48ef47239086250781e84446f 0.600000000000 1801253 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": 1313622, "vin": [ { "gen": { "height": 1313612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "015a9b42b4e25a97325c6225c0fd82c5c266cec48ef47239086250781e84446f" } } ], "extra": [ 1, 250, 73, 21, 18, 5, 103, 163, 111, 221, 53, 244, 49, 50, 159, 106, 44, 252, 166, 165, 21, 109, 14, 206, 47, 207, 141, 136, 249, 158, 52, 229, 215, 2, 17, 0, 0, 0, 7, 191, 81, 178, 162, 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