Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35a37b51f92e84fc033ed2288fa69221ab9f2f0502af8cdf1de49ed41419dde7

Tx prefix hash: 765e5a435609b1960fb450813b8219c6348170369e546e7679cf08968d52c983
Tx public key: 10a1d7a87760751451a202d652d6ce2a0f2f42a20c5aa33fd9debee224560789
Timestamp: 1765057081 Timestamp [UCT]: 2025-12-06 21:38:01 Age [y:d:h:m:s]: 00:027:17:17:13
Block: 1427963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19864 RingCT/type: yes/0
Extra: 0110a1d7a87760751451a202d652d6ce2a0f2f42a20c5aa33fd9debee224560789021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 073415fdd82f1203bf5edc4e3abf05df9b017afd9ae739f56afe5bd7f19d8e19 0.600000000000 1916670 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": 1427973, "vin": [ { "gen": { "height": 1427963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "073415fdd82f1203bf5edc4e3abf05df9b017afd9ae739f56afe5bd7f19d8e19" } } ], "extra": [ 1, 16, 161, 215, 168, 119, 96, 117, 20, 81, 162, 2, 214, 82, 214, 206, 42, 15, 47, 66, 162, 12, 90, 163, 63, 217, 222, 190, 226, 36, 86, 7, 137, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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