Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbc1781b06d834e8bf75f121998d8b4f796a1d40384570fa7a8375ca3b8ef7e0

Tx prefix hash: 7be9125a348c729fde968faee45e0bc53ad18c348835a21e75a4cd58b80e3b3c
Tx public key: d99e1e3f03744cc55db13fb80298b35950755128d8db4dd888324ccd09090717
Timestamp: 1697179232 Timestamp [UCT]: 2023-10-13 06:40:32 Age [y:d:h:m:s]: 01:177:23:34:30
Block: 868564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388224 RingCT/type: yes/0
Extra: 01d99e1e3f03744cc55db13fb80298b35950755128d8db4dd888324ccd09090717021100000010faf35c9c000000000000000000

1 output(s) for total of 0.812993249000 dcy

stealth address amount amount idx
00: fba4dc9404ae35dc3da32a76b60048d2e33691d0f4492c96279a0a77e9b4a025 0.812993249000 1323379 of 0

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": 868574, "vin": [ { "gen": { "height": 868564 } } ], "vout": [ { "amount": 812993249, "target": { "key": "fba4dc9404ae35dc3da32a76b60048d2e33691d0f4492c96279a0a77e9b4a025" } } ], "extra": [ 1, 217, 158, 30, 63, 3, 116, 76, 197, 93, 177, 63, 184, 2, 152, 179, 89, 80, 117, 81, 40, 216, 219, 77, 216, 136, 50, 76, 205, 9, 9, 7, 23, 2, 17, 0, 0, 0, 16, 250, 243, 92, 156, 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