Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf5e76fb0ebcbd721d93d1b4f5798548b7c6fbd55bfff6945a6261cf24bd306e

Tx prefix hash: cb012a85137d623d847c87afc8d4e80d19de0512dd20a770f961bec0fca1a609
Tx public key: f71cfb15224ed761c749b4ea0b9ac4197a525b721ccd5ccee870cdb78e49b42c
Timestamp: 1761119944 Timestamp [UCT]: 2025-10-22 07:59:04 Age [y:d:h:m:s]: 00:069:00:37:59
Block: 1395345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49425 RingCT/type: yes/0
Extra: 01f71cfb15224ed761c749b4ea0b9ac4197a525b721ccd5ccee870cdb78e49b42c02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1500558fcf13a1f2a4ba465a90df593993848f60bc3ba28a44330a403f6f5f9 0.600000000000 1883622 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": 1395355, "vin": [ { "gen": { "height": 1395345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1500558fcf13a1f2a4ba465a90df593993848f60bc3ba28a44330a403f6f5f9" } } ], "extra": [ 1, 247, 28, 251, 21, 34, 78, 215, 97, 199, 73, 180, 234, 11, 154, 196, 25, 122, 82, 91, 114, 28, 205, 92, 206, 232, 112, 205, 183, 142, 73, 180, 44, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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