Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20f6d1987dc72c803707db04d75f9b68a2f6f0012852f8752beb72eae949f00f

Tx prefix hash: 2c9c09ab30d87c6c0d86a8f5baf9e920adb96aeacfb5747c8a7fc335fcc3ae26
Tx public key: d727f5540d2e8876e9f84a7454e61336f6605dc7b75e6c9b38285309c569e088
Timestamp: 1760499753 Timestamp [UCT]: 2025-10-15 03:42:33 Age [y:d:h:m:s]: 00:031:09:14:05
Block: 1390205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22465 RingCT/type: yes/0
Extra: 01d727f5540d2e8876e9f84a7454e61336f6605dc7b75e6c9b38285309c569e0880211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f64caf8835fd1e30ffebe1ac9b2c314b77959dc502f304251ca2842af88dd9f 0.600000000000 1878438 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": 1390215, "vin": [ { "gen": { "height": 1390205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f64caf8835fd1e30ffebe1ac9b2c314b77959dc502f304251ca2842af88dd9f" } } ], "extra": [ 1, 215, 39, 245, 84, 13, 46, 136, 118, 233, 248, 74, 116, 84, 230, 19, 54, 246, 96, 93, 199, 183, 94, 108, 155, 56, 40, 83, 9, 197, 105, 224, 136, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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