Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f905307bdb25f857c626d14c1f1b9f513b0b17d30d7c6af1e2652cc04f9bba78

Tx prefix hash: d270455fe078496a57c9556d163f56a8856d46c111654f8262b7dacfb2552a35
Tx public key: f7e510ed2c552abaf082a8a2c45ecd044f3d58f4d611da42652031865b140818
Timestamp: 1727533039 Timestamp [UCT]: 2024-09-28 14:17:19 Age [y:d:h:m:s]: 00:186:12:27:20
Block: 1120019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133090 RingCT/type: yes/0
Extra: 01f7e510ed2c552abaf082a8a2c45ecd044f3d58f4d611da42652031865b140818021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d73eec096f9e51471bdfef0be8956351439903075c24a20b56b6c24c8fe53e5 0.600000000000 1601784 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": 1120029, "vin": [ { "gen": { "height": 1120019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d73eec096f9e51471bdfef0be8956351439903075c24a20b56b6c24c8fe53e5" } } ], "extra": [ 1, 247, 229, 16, 237, 44, 85, 42, 186, 240, 130, 168, 162, 196, 94, 205, 4, 79, 61, 88, 244, 214, 17, 218, 66, 101, 32, 49, 134, 91, 20, 8, 24, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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