Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6294ed077131e99299288ef3ab7d7f5e481bdb2715f07f76c989aba9a82de96d

Tx prefix hash: 74bd47f1366d710eda06b0db583dc40703f3274e1a510c8a3f2c47fae42b7275
Tx public key: 9c81aba4fa9abd509646195caaf0de537dea1b614e65b6c4fcf5eb38b06ba355
Timestamp: 1738208244 Timestamp [UCT]: 2025-01-30 03:37:24 Age [y:d:h:m:s]: 00:139:10:43:05
Block: 1208087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99610 RingCT/type: yes/0
Extra: 019c81aba4fa9abd509646195caaf0de537dea1b614e65b6c4fcf5eb38b06ba35502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba9b1690db09c57fd8d28379dc872d639d8067883b4cda975cb88c522bc7b1d1 0.600000000000 1694814 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": 1208097, "vin": [ { "gen": { "height": 1208087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba9b1690db09c57fd8d28379dc872d639d8067883b4cda975cb88c522bc7b1d1" } } ], "extra": [ 1, 156, 129, 171, 164, 250, 154, 189, 80, 150, 70, 25, 92, 170, 240, 222, 83, 125, 234, 27, 97, 78, 101, 182, 196, 252, 245, 235, 56, 176, 107, 163, 85, 2, 17, 0, 0, 0, 1, 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