Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36e9b0440825a040885998d24fcd912670bad2e86d3d3de018bfc4ac67c41a85

Tx prefix hash: f62b06d365d2e85fe3b9b79e7ffb510df6d272414cedeb5ecac3b978cf054791
Tx public key: 18d8d175f88e48ea29c4782f282cdc8f3bb609c8bc7d7e84320b2d7765ca1faa
Timestamp: 1763318744 Timestamp [UCT]: 2025-11-16 18:45:44 Age [y:d:h:m:s]: 00:051:17:20:00
Block: 1413563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37043 RingCT/type: yes/0
Extra: 0118d8d175f88e48ea29c4782f282cdc8f3bb609c8bc7d7e84320b2d7765ca1faa02110000000143b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c126d4a15f9cdda4190438cbe76554a60c194b41b7a48eae8b6a72a7c924a963 0.600000000000 1902042 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": 1413573, "vin": [ { "gen": { "height": 1413563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c126d4a15f9cdda4190438cbe76554a60c194b41b7a48eae8b6a72a7c924a963" } } ], "extra": [ 1, 24, 216, 209, 117, 248, 142, 72, 234, 41, 196, 120, 47, 40, 44, 220, 143, 59, 182, 9, 200, 188, 125, 126, 132, 50, 11, 45, 119, 101, 202, 31, 170, 2, 17, 0, 0, 0, 1, 67, 181, 4, 113, 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