Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6df9bd2d4cb3b1d79af194534480ad3e0d2172aee579c6d049a1f544e2671c46

Tx prefix hash: 0a1090520b559d38188eacc66fa391cb969226a3b3f86b35ea0ca37fc9a928cc
Tx public key: d4fba4f1e2be63121749af4b456db5eda470e4a6c52fd7eaad187f4740b9f659
Timestamp: 1718484793 Timestamp [UCT]: 2024-06-15 20:53:13 Age [y:d:h:m:s]: 00:277:05:43:22
Block: 1045006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198114 RingCT/type: yes/0
Extra: 01d4fba4f1e2be63121749af4b456db5eda470e4a6c52fd7eaad187f4740b9f659021100000001befa2d88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4d5e4f4ca5c0bc2126ce45af188226c554db2288b171fd9fa9452d23a6396cf 0.600000000000 1514467 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": 1045016, "vin": [ { "gen": { "height": 1045006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4d5e4f4ca5c0bc2126ce45af188226c554db2288b171fd9fa9452d23a6396cf" } } ], "extra": [ 1, 212, 251, 164, 241, 226, 190, 99, 18, 23, 73, 175, 75, 69, 109, 181, 237, 164, 112, 228, 166, 197, 47, 215, 234, 173, 24, 127, 71, 64, 185, 246, 89, 2, 17, 0, 0, 0, 1, 190, 250, 45, 136, 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