Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88c37c52beb01fd4d1c69b270d7bb9aa303e99c5924fb73ea030b7beba5a237f

Tx prefix hash: f5c4fe3f731558ab0cfbd9e1bc125fc7bf685b397d5fc8f75d44c02b0314b761
Tx public key: 9e07e33ebbfcac79824d1f66bfb4c6aabd1da13bbc7ab27682e3a187f5167348
Timestamp: 1764348345 Timestamp [UCT]: 2025-11-28 16:45:45 Age [y:d:h:m:s]: 00:061:13:08:00
Block: 1422101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43888 RingCT/type: yes/0
Extra: 019e07e33ebbfcac79824d1f66bfb4c6aabd1da13bbc7ab27682e3a187f5167348021100000003da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e4c5df0eac239985ee9f2d9271ae9d6265ed9f7dd0f07bcfb4cd35bbb6f5d35 0.600000000000 1910666 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": 1422111, "vin": [ { "gen": { "height": 1422101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e4c5df0eac239985ee9f2d9271ae9d6265ed9f7dd0f07bcfb4cd35bbb6f5d35" } } ], "extra": [ 1, 158, 7, 227, 62, 187, 252, 172, 121, 130, 77, 31, 102, 191, 180, 198, 170, 189, 29, 161, 59, 188, 122, 178, 118, 130, 227, 161, 135, 245, 22, 115, 72, 2, 17, 0, 0, 0, 3, 218, 85, 72, 72, 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